fix(webapp): stop logging full batch item contents in batchTriggerV3 - #4404
Conversation
|
7f5f033 to
a978755
Compare
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
💤 Files with no reviewable changes (1)
📜 Recent review details⏰ Context from checks skipped due to timeout. (18)
WalkthroughRemoved a debug log in the batch trigger service that recorded the full 🚥 Pre-merge checks | ✅ 3 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (3 passed)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
The idempotency grouping step logged every batch item verbatim, including its payload and options (which can carry arbitrary customer metadata). Replace that with a summary of task identifiers and item counts, and add a unit test covering the summary shape.
7a8a5c7 to
89d0eaa
Compare
@trigger.dev/build
trigger.dev
@trigger.dev/core
@trigger.dev/python
@trigger.dev/react-hooks
@trigger.dev/redis-worker
@trigger.dev/rsc
@trigger.dev/schema-to-json
@trigger.dev/sdk
commit: |
Summary
The idempotency grouping diagnostic now records task identifiers and item counts rather than full batch items. This keeps the log useful for troubleshooting without including payloads or options.
Performance notes
Should be better than baseline.